Overview

Information presented by the MOMI PC Client is obtained from server processes running on the NonStop System. Some process run continually and others are started on demand.

The MOMI subsystem on the NonStop System is initially started via the TACL obey file OBYMOMI located in subvolume where MOMI is installed. This obey file starts the main $MOMI process which serves as the overseer for the subsystem. This main process:

configures a master measurement in the MEASURE subsystem

starts an Expand collector process

starts a collector in each processor of the system

starts a process that writes history to the HST01DB file

starts a process that performs the history consolidation and deletion

starts an NSKCOM process for obtaining virtual memory statistics

posts a 'listen' on the assigned TCP/IP process(es) and port(s) for incoming connections from the client

The MOMI PC Client communicates with the server by issuing a TCP/IP connect to the configured address and port of the $MOMI server. This main server either provides information directly or it may pass the request off to another server it started. The response is returned to the main server which in turn is sent back to the PC Client.

Sensitive commands that require security are executed in the context of the User ID provided. When a user logs on, a server assigned to that particular client executes the logon command and assumes the authority of that particular user. From that point on, sensitive commands are executed by that server or a server it started.

The MOMI server object may execute dynamic SQL/MP statements to obtain information from the system and user catalogs. The statements are used in support the PC MOMI Client screens Files / SQL/MP / *. The TACL obey file OBYCSQL performs an SQL/MP compile of the MOMI server object with the attribute of NOREGISTER ON. This means that the SQL/MP catalog do not reflect the MOMI executable.